Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove support for variable PCAP filenames #698

Merged
merged 1 commit into from
Mar 22, 2024

Conversation

peter-oneill
Copy link
Contributor

Fixes issues #576, #610, #673

The original variable PCAP filenames PR #521 would free and rewrite a single per-scenario-action block of memory for every call, but all calls would continue referencing the memory. This led to various use-after-free issues. The PCAP play design also isn't set up for loading a file per call, so the solution didn't scale well.

This PR removes the variable PCAP filenames feature, while retaining the variable RTPStream filenames feature, which doesn't have the same issues.

Specific testing done:

  • that PCAP play is fixed
  • that RTPStream continues to work, with files specified as any of:
    • <exec rtp_stream="my_audio.wav"/>
    • <exec rtp_stream="[field0]"/>
    • <exec rtp_stream="[command_line_key]"/>

@orgads
Copy link
Contributor

orgads commented Mar 20, 2024

Thank you very much @peter-oneill!

Please add a release note.

@peter-oneill peter-oneill force-pushed the remove-pcap-play-variable-filename branch from bd179d8 to b33903f Compare March 21, 2024 10:41
@orgads orgads merged commit 5e57d81 into SIPp:master Mar 22, 2024
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

segmentation fault on playing pcap file ( sipp 3.7.2 ) SIPp giving segmentation fault.
2 participants